Feature/idaas 748/add login alternative key#624
Conversation
rafarubim
requested review from
RodrigoTadeuF,
gabpaladino and
leo-prange-vtex
and removed request for
a team
|
Hi! I'm VTEX IO CI/CD Bot and I'll be helping you to publish your app! 🤖 Please select which version do you want to release:
And then you just need to merge your PR when you are ready! There is no need to create a release commit/tag.
|
|
Beep boop 🤖 I noticed you didn't make any changes at the
In order to keep track, I'll create an issue if you decide now is not a good time
|
iago1501
left a comment
iago1501
left a comment
There was a problem hiding this comment.
@rafarubim , can you add the changelog with this change, please 🙏🏻
|
Your PR has been merged! App is being published. 🚀 After the publishing process has been completed (check #vtex-io-releases) and doing A/B tests with the new version, you can deploy your release by running:
After that your app will be updated on all accounts. For more information on the deployment process check the docs. 📖 |
2 participants
What problem is this solving?
This adds
vtex.login-alternative-key:login-contentas a possible block to render as child ofstore.loginHow to test it?
Go into the rafaprtest2 workspace and check that nothing in the store is broken, and the login still renders correctly in the
/loginpage:Then, go into the rafaprtest workspace and check that nothing in the store is broken, and the
vtex.login-alternative-keyrenders correctly in the/loginpage:How does this PR make you feel?